I am having an issue with the SP2 upgrade. Our netbios domain name has a dot or period in it - "domain.com". When the install script checks to see if there is an account in SQL for the server, it chops off the .com". The log shows this: Adding a login for SMS Site Server: IF NOT EXISTS (select * from master.sys.server_principals where name='DOMAIN\SERVER01$') CREATE LOGIN [DOAMIN\SERVER01$] FROM WINDOWS If I run that query manually against the SQL server, it fails. But if I substitute the correct "DOMAIN.COM\SERVER01", it will create the account. Any thoughts how I can get around this?

All AD FQDN'shave a dot in them it's a requirement and has been since Windows 2000 server introduced AD.I generally use .local and never use .com but I don't see why it would matter. Does this stop the upgrade or just give a warning?John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum

This stops the upgrade. And nothing is workign now. I believe it is connecting via netbios name. Whatever it is doing, it is trying to create/check for an account that id DOMAIN\SERVER01$ which will not work. It has to be DOMAIN.COM\SERVER01$ as that is the netbios name of the domain. Thanks for the reply

Although the NetBIOS name is technically legal, the period in it is certainly the source of the issue. You will have to call CSS to get this resolved.I hope for your sake this is a test domain, as this will cause you major pain in many products.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

What am I missing here? All my domains are .something.John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum

Unfortunately it is production. I inherited it.

What am I missing here? All my domains are .something. John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum that is your dns name. what happens when you type nbtstat -n? My guess is that the Group will not have a dot in it.

http://support.microsoft.com/default.aspx/kb/909264John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum

jbmurphy,Did you ever find a resolution to this dotted domain issue? We are running into the EXACT issue trying to install SP2 of SCCM2007. Any insight would be greatly appreciated!!!I can be reached directly at: darin.nelson@anokaramsey.eduDarin

Hello, Latest info on this is:This happens when the NETBIOS name contains a dot in it "." which makes it look as a FQDN name, which is not.For example we can have a netbios name of domain.com, and the FQDN of the domain could be domain.test.com or anything you like.The problem is that EMC does a FQDN check when launching and it sees the netbios name as a fqdn ( because it uses that format ) so the EMC will fail because there is no such FQDN . There is currently a bug opened with MS and it is scheduled for RU4 .The fix will remove the FQDN check so the naming format should no longer play a role.In the meantime the only workaround is to continue to use powershell as this is not impacted by the behaviour.Hope it helps, Mihai

EMC .. RU4 Are you talking about System Center Configuration Manaegr 2007?

Hello, Sorry, I didnt really pay attention to the forum section. In my case i was talking about the Exchange Management Console for E14. But as this happens also with other management consoles...I guess that they should have something on System Center also.Still, my post was about E14.Thanks, Mihai

Did you ever find a work around for this? I also have this same issue where the NETBIOS name of my domain ends in .COM

Rename you domain according to best practices. Calling CSS is going to be your best bet (although my money is on them telling you the same thing).Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Yes, well renaming the domain isn't an option at this point. We would rather do without this software than break everything that's already calling something by our current NETBIOS name. How about a hotfix or KB article for this issue? I would prefer not to have to spend $200 for the privilage of finding out if some sort of fix or work around exists or not.